Fix DATERANGE parser handling of clientAttrs
property
#5891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will...
Replace the
AttrList
classclientAttrs
property with a getter so that theDateRange
constructor does not confuse the property with other attributes when merging DATERANGE tags with the same ID.Why is this Pull Request needed?
Fixes logger warning
DATERANGE tag attribute: "clientAttrs" does not match for tags with ID: "${DATERANGE ID}"
.hls.js/src/loader/date-range.ts
Lines 41 to 50 in 470a29f
It also improves Typing since
clientAttrs
was treated asany
but could have beenstring[] | undefined
. Now it is alwaysstring[]
as it was expected to be in the m3u8-parser:hls.js/src/loader/m3u8-parser.ts
Lines 551 to 554 in 470a29f
Are there any points in the code the reviewer needs to double-check?
clientAttrs
is only read in one place (above when parsing a new DATERANGE) so the impact of filtering attribute names in the getter should be minimal and hopefully offset by faster instantiation ofAttrList
instances.Resolves issues:
Checklist